home *** CD-ROM | disk | FTP | other *** search
- Path: wcap.centerline.com!vajra!chase
- From: chase@centerline.com (David Chase)
- Newsgroups: comp.object,comp.lang.c++,comp.lang.java
- Subject: Re: Java: What's the Big Deal?
- Date: 25 Mar 1996 17:33:17 GMT
- Organization: CenterLine Software
- Distribution: world
- Message-ID: <4j6lct$7p5@wcap.centerline.com>
- References: <4iuvkn$7it@news4.digex.net>
- Reply-To: chase@centerline.com
- NNTP-Posting-Host: vajra
-
- In article 7it@news4.digex.net, ell@access4.digex.net (Ell) writes:
- > Erik P. DeBenedictis (erikd@netalive.com) wrote:
- > : The idea of putting functions (or applications) on Web pages so they can
- > : be accessed by the public, but without the possibility of introducing
- > : Trojan Horses or viruses, is much newer. I believe this is a "Big Deal."
-
- > : However, Java's secure bytecode is not the only way to do this.
-
- > What is/are?
-
- Software fault isolation (aka sandboxing) can also be used to do this.
- It's got some advantages from a backwards compatibility point of view,
- but you don't get some of the other nice stuff that Java brings along
- (garbage collection and threads, for starters. Also, platform-independent
- semantics).
-
- Another choice is just to emulate a PC, no matter what the platform.
-
- Yet another choice, sort of, is ANDF.
-
- In either case, you'd also need to be sure to provide a proper "secure"
- OS interface for the application to interact with the rest of the
- world. Note that this is the hard part (where have the Java security
- bugs been?) -- designing a safe language is not as easy as falling off
- a log, but it isn't that difficult if you know what you are doing and
- borrow heavily from the prior art.
-
- speaking for myself,
-
- David Chase
-
-